refactor: establish tool and event ABI contracts - #1404

Summary

• Move provider-neutral Tool ABI snapshot contracts into bitfun-agent-tools, including provider identity, no-input default effect facts, cancellation facts, and stale-call guards.
• Preserve static provider group identity in materialized tool snapshots while keeping dynamic and static provider classification distinct.
• Move the AgenticEvent projection manifest and legacy WebSocket allowlist into bitfun-events, leaving WebSocket transport as delivery only.
• Tighten boundary checks and update the decomposition plan/completed archive to reflect the completed Public API and Tool/Event ABI foundation.

Risk

• Intended as a behavior-preserving refactor: tool execution, event payload shape, and transport delivery semantics are unchanged.
• Tool effect facts are explicitly no-input defaults; execution-time admission and batching remain tied to existing input-aware tool methods.
• Agentic projection manifest is scoped to AgenticEvent frontend projection, not host-only stream or ACP extension event surfaces.

Verification

• cargo test -p bitfun-agent-tools --test tool_contracts
• cargo test -p bitfun-events
• cargo test -p bitfun-transport websocket
• cargo test -p bitfun-agent-runtime
• cargo check -p bitfun-core --no-default-features
• cargo check -p bitfun-core --features product-full
• node --test scripts/check-core-boundaries.test.mjs
• node scripts/check-core-boundaries.mjs
• pnpm run check:repo-hygiene
• git diff --check
• git diff --cached --check